introduce @_manualOwnership performance attribute #81858
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This attribute forces programmers to acknowledge every copy that is required to happen in the body of the function. only those copies that make sense according to Swift's ownership rules are "required". For example,
The way this is implemented is to flag every implicitly-created copy by SILGen in a function as an error. This keeps SILGen and the Swift language in sync about what copies are actually happening, which motivates fixes for cases where SILGen can be more clever.
This also means that there is no hand-holding to avoid exclusivity violations. Static checking will continue to catch some cases, but for other cases, like class objects, it is up to the programmer to understand where they may need to rewrite code with mutable references. This is where the "manual" comes from. For example,